home *** CD-ROM | disk | FTP | other *** search
- Path: access4.digex.net!not-for-mail
- From: ell@access4.digex.net (Ell)
- Newsgroups: comp.object,comp.lang.c++
- Subject: Re: how many classes are too much? trying to follow Robert Martin's advice
- Date: 12 Mar 1996 05:14:49 GMT
- Organization: The Universe
- Message-ID: <4i3189$gr6@news4.digex.net>
- References: <4hn86s$im4@netlab.cs.rpi.edu> <4i1fim$bm5@netlab.cs.rpi.edu>
- NNTP-Posting-Host: access4.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- Robert C. Martin (rmartin@oma.com) wrote:
- :...
- : Certainly there are costs. You have named them. Your design is
- : getting more complicated. (Interesting isn't it. When the design
- : becomes more complex, the code gets simpler. Complex problems require
- : complex expressions.) Your makefiles are more complex. You need some
- : way to manage all the source files.
- :
- : Now ask yourself if there is a net gain. Is the system overall easier
- : to deal with?
-
- In most cases where the complexity of a C++, or other oopl, project has
- been previously addressed, the solution can be made into a library -
- static or dynamic - which subsequent programmers can use with less
- complexity. This is a major part of the component and object reuse
- motivation. So that the design of similar future projects in the domain
- are not generally as visibly (code weight wise) complex.
-
- Elliott
-
-